Task: Unit Test Execution
After producing the required test assets, the activity should be the execution of test cases, activity performed by Testers, in order to find errors in the component code.
Disciplines: Unit Testing
Purpose
This activity is basically stated under the purpose of finding errors in the code.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    		Optional:
      Outputs
        Main Description
        Test Execution is the activity stated in order to find errors placed in the code by developers. Testers use test cases, test scripts (when execution is automated) and test suites as main artifacts. If, along test execution, errors are found, testers should report them to be further fixed by component developers, through Change Requests (CR).
        Steps
        Perform tests for each method
        The first step is to test each method, individually.
        Perform tests of the integration of methods contained in a class
        Secondly, test the integration of the methods contained in the class.
        Perform tests of the integration of classes contained in a component
        Later, all the classes which compose the component must be integrated and tested.
        Associate a Change Request (CR) to an error, if it was found
        Whenever an error is found, the tester must associate the error with a Change Request (CR).
        Key Considerations
        This activity can be conducted both manually and automatically, following what is described in the test plan, which meets major organizational needs.